New Design vs. Upgrading from VS Legacy

• In most cases, it is possible to completely reuse audio, video and non VisionSuite control processing when upgrading your design. Things to consider are:
  • Control programming that interfaces via named components with ACPR and Seervision plugins
  • Custom scripts that interface directly with Seervision’s public websocket API
  • Advanced programming that enabled room division use cases
  • Control scripts for UCIs to enable automatic and manual modes
  • In general, most custom programming will have to be reimplemented when upgrading an existing VS Legacy system - this will take additional time. Please see the best practices guide for highlevel time estimates and how to update an existing system here: <need link to new page>

UC Compatibility

• Using the Q-SYS Connect component there are several UC platforms that are drop in compatible with VisionSuite. Standard UCI and control programming can be used to incorporate VisionSuite seamlessly with your UC platform of choice:
  • Microsoft Teams Room
  • Zoom Rooms
• Incorporate Call Sync into your VisionSuite system to seamlessly show status of the system on NL-SB42 speakers and TSC Generation 3 touchpanels
• Additional functionality may require advanced Lua scripting to extend the base feature set of VisionSuite in your room.
• Incorporate as many Q-SYS USB bridging and Mediacast to HDMI endpoints as necessary. Only a single Mediacast output from the VS component is supported at this time, but you can implement any “one-to-many” applications as needed.

Plugins

• Seervision and ACPR plugins should not be used alongside the VisionSuite component. VS Native is not compatible in the same design with VS Legacy applications.
• Several 3rd party plugins can be used with VisionSuite systems as is standard in Q-SYS installs. Be cautious of adding several process intensive plugins to any core serving as the connection point to VisionSuite Designer. Ensure you maintain a safe compute and control usage during normal runtime. Advanced statistics are observable by changing the core status component property Verbose = Yes.

1. Open Q-SYS Designer and create a design file:
2. Add all hardware to your design:
   1. Add a VSA-100
   2. Add your cameras
      1. Camera properties
         1. Set IP streaming to Multicast Only
      2. Camera controls settings (in QSYS design at runtime under “Status”)
         1. Set Flow Control to Off  
         2. Set Traffic Shaping to On
   3. Add a VisionSuite component
   4. Wire your cameras to the Mediacast inputs of the VisionSuite component

      Note

      Cameras must be wired in the schematic and must have the correct Input number to use the Ceiling Mounted checkbox. Each camera must have a unique Input number. This also applies for emulation.

       
   5. Wire the VisionSuite component’s Mediacast Output 1 to one more Mediacast destinations in any “one-to-many” configuration. Mix and match multiple USB video bridges or NV-based Mediacast to HDMI as needed for your application.
3. Add all microphone channels into your design:
   1. Optional: Add the MXA920 / TCC2 plugins into the design (Q-SYS Library)

      Warning

      Sending AEC reference back to the TCC2 will result in a talker position directly below the microphone when the far end is talking. In most cases, this results in a poor user experience and is not recommended.

       
   2. Configure audio routing and processing for the microphones.

      Caution

      Avoid on-board microphone processing as much as possible. Certain on-board microphone processing will delay the audio stream but not the talker’s coordinate data. This can cause mismatches in audio received vs. audio detections.

       
4. Design your audio processing and understand your room acoustics
   1. Understand any acoustic challenges or sonic issues in your space before you design the audio processing. If possible, apply physical acoustic treatment to the room to reduce audio reflections and acoustic anomalies to improve the effectiveness of all stages of audio processing.
   2. VAD Input
      1. Design your VAD processing to be responsive and low noise. The VAD input must be broadly intelligible and well optimized for speaker detection. We recommend utilizing a Gating Automatic Mic Mixer for best performance.
      2. With no talker audio, verify the meters show ~0 dB signal-above-noise when nobody speaks. If they don't, check upstream gain staging. For scenarios with constant noise / HVAC, apply more noise reduction in the in the AEC component as needed.
      3. Have someone speak at normal volume; the gate should open cleanly. Whisper; decide if you want whispers to trigger the gate. Adjust threshold accordingly.
      4. Have someone speak with natural pauses. If the gate closes while the person pauses, increase hold. If it feels sluggish switching to another speaker, decrease it.
      5. Depth = 60 dB.
      6. Last Mic On = Enabled
      7. Max NOM = 1
         1. Typically ensures only one mic is correlated with the incoming coordinate data
   3. Speakerphone Out
      1. Design your Speakephone Out processing to be natural and transparent. We recommend utilizing a Gain-Sharing Automatic Mix Mixer.
      2. With no talker audio, note the ambient level on meters, then set threshold ~6 dB above that.
      3. Start at Depth = −15 dB. Have one person speak; listen for background noise from inactive channels. Increase depth only as needed.
      4. Have two people alternate speaking. If the handoff sounds choppy, increase hold time. If it feels sluggish, decrease it.
      5. Leave Attack at 5 ms unless you hear plosive artefacts.
   4. Speakerphone In
      1. Ensure the audio level is appropriate and the gain in the speakers is loud enough to be clearly heard in the room. Minor EQ adjustments may be applied before the speaker output if the room has acoustic challenges.
   5. Far-End Input
      1. Design your Far-End processing to be responsive and low noise. The Far-End input must be broadly intelligible and well optimized for speaker detection. We recommend utilizing an additional gain component to ensure proper audio level enters the VisionSuite component.
   6. Due to issues with excessive frame freeze when cameras are switched, NV-21-HU USB bridges are not recommended at this time.
   7. Only one Mediacast output is supported per VisionSuite component at this time.

For more information, see Q-SYS Quantum Level 1 Training (Online).

In emulation mode, double-click the VSD component to open the VisionSuite Designer interface.

1. Create a Room and create a Config, giving them friendly names

2. On your floor, upload the floorplan and click ‘calibrate scale’
   1. Place your blue dots at a known measurement and type in the actual distance to calibrate

      Tip

      Once you’ve imported the floorplan, move it by clicking and dragging so that the origin (0,0) of the project starts at the bottom left corner of the room’s floorplan. This way, when you start placing devices and furniture, their values will all be positive relative to the origin.

      

       

3. On the room, set the room dimensions via the room zone and under Room shape set the room height (min and max).
4. Go to Inventory and add all your devices:
   1. Add all cameras, and if known, their rough location in the room.
      1. Specify each camera’s type:
         1. Speaker Spotlight (Audio Driven)
         2. Presenter Tracking (Vision Driven)
         3. Conductor (Vision Driven Overview)

            Note

            Up to 14 Audio Driven (Speaker Spotlight) cameras and 1 Presenter Tracking, and 1 audience-facing conductor camera is supported.

             
   2. Add all ceiling microphones

      Note

      Up to 8 ceiling microphones are supported.

       
   3. Add the VisionSuite Accelerator
   4. Configure each device's properties accordingly

5. Optional: Add furniture and displays into your room to have a 3D reference of the layout.

Depending on the automation, different container types and container settings are optimal

Overview

Zones define:

• Where VisionSuite focuses attention
• What areas are ignored
• How cameras respond to detected activity

Speaker Zones

Speaker Zones monitor audio activity within a defined area. When speech is detected inside a zone, VisionSuite can trigger a corresponding camera action.

Best Practices

• Place zones at speaking locations
  • Cover areas such as seats, presentation spots, or audience sections.
• Use generously sized zones
  • Avoid small or tightly defined zones. Tight boundaries can lead to unstable talker detection, causing delayed or erratic camera switching.

Zone edges should not align exactly with seating positions. Instead, include a buffer around each subject area to account for natural movement (e.g., people shifting in their seats) and microphone localization variance.

This helps ensure that:

• Speakers remain within the zone even as they move
• Minor detection drift does not trigger incorrect zones or missed activations
• Account for coordinate drift
  • Microphone positioning is approximate (±20–30 cm), not exact. Slightly larger zones help maintain reliable detection.
• Plan camera coverage
  • Assign zones to cameras that have clear sightlines, ensuring natural, frontal shots when triggered.

Creating Speaker Zones

1. Open the Speaker Zone on the left sidebar
2. Click the “+” (Add) icon
3. Select the newly added zone and on the right sidebar the configuration of the zone should be visible:
4. Select the Trigger type on the right sidebar
5. Position the zone by adjusting its corner points or by enabling the Move entire zone option and moving the entire zone shape
6. Assign a descriptive name

In addition to standard Speaker Zones, there is another type available under Type:

Spotlight Exclusion

The Spotlight Exclusion zone is used to ignore audio detections within a defined area. Any speech or noise originating inside this zone will not trigger speaker-based rules or camera actions.

This is particularly useful for filtering out:

• Persistent background noise sources
• Audio reflections or reverberation artifacts
• Areas where localization is unreliable

Example

In a room with an oval table, detections may drift toward the center due to microphone approximation. Placing a Spotlight Exclusion zone in the center prevents false triggers from that region.

Presenter Zones

Presenter Zones are used for camera behaviors related to presenter tracking and framing. Unlike Speaker Zones, which rely on audio activity, Presenter Zones are primarily driven by visual tracking and camera behavior.

• They can be created in Emulation Mode
• Their shape can only be finalized on-site, once the system is connected to the cameras

Presenter Zone Types

There are three types of Presenter Zones:

• Trigger Zones
• Exclusion Zones
• Tracking Zone

Detailed configuration and behavior for these zones are covered later during the on-site setup phase.

Overview

Rules define how camera automation behaves in VisionSuite.

A rule links:

• An Event (e.g., activity within a zone)
• To an Action (e.g., triggering a container, switching cameras)

In essence:

Event → Action

Prerequisites

• Ensure Speaker Zones are defined
• Ensure cameras are logically assigned to cover each zone

Rules can be created from the right-hand panel after selecting your configuration.

Once the microphones are installed in the room, it is important to configure them properly in their native interfaces.

Room calibration is the foundation of VisionSuite Features performance. This process helps cameras and microphones understand where they are in relation to each other and to the room, so the system can combine their data and accurately locate people. Fortunately, this doesn’t require manual measurements. Calibration uses ArUco markers - QR-code-like patterns - that let cameras determine their position just by viewing the marker. With a little user assistance, the cameras can also calibrate the microphones by observing them (more on that later).

Calibration Process

1. Place one printed out Aruco Marker near your room origin.
2. Point a camera at that marker and let it determine it’s location based on that marker.
3. Use the same camera to auto-calibrate your microphone.
   1. If the camera can’t see the mic properly, or just at a flat angle, measure the location of the mic manually and fill in this info.
   2. In any case, measure the mics height and input that value manually
4. Validate the detection-matching of this camera-mic pair.
5. Place a marker central in the “working area” of the cameras that cover this mic’s working area. In most cases it should be placed flat at the center of your table:
6. Calibrate all cameras with the central marker.
7. One by one, validate the detection-matching of each camera with the mic data.
8. Repeat the steps 3-7 for all additional Microphones and Cameras that you might have. As you add the mics, isolate them by disconnecting all other mics in VSD and test the performance to make sure THAT mic works well. (change port no. or IP)

Best Practices & Troubleshooting

Once the cameras and microphones are correctly calibrated, and you’ve set up your Speaker Zones and corresponding rules as covered in the ‘off-site’ section, it’s time to verify that the logic works.

In this step, speak from different positions in the room, making sure to test different seats in all of the different Speaker Zones created.

Make sure to also test multiple speakers simultaneously and people interrupting each other.

If everything has been properly set up, you should see the active speaker being framed in your desired shots. In this step, you can tweak your shot containers, including framing, shot safety, settle time, and speaker height to better meet your needs now that you see how the shots are applied.

Under the visualizations tab in the left-hand side panel, you can enable the visualizations of the detections to see the person uncertainty, the microphone raw data, and the camera raw data and get a better understanding of what VisionSuite is seeing and hearing relative to the space.

In the Room tab (the parent of the config), you can also adjust the global settings that govern the automation in your room.

Speaker Fadeout

Speaker Fadeout determines how long a person’s detection remains active after they’ve finished talking.

In the case of a longer Speaker Fadeout, if a person is interrupted, a camera may stay on the old (current) speaker for longer, waiting for the fadeout time to run out before switching the camera to the new speaker.

A Speaker Fadeout time of 2 seconds is recommended to account for short pauses when someone speaks.

If a lot of crosstalk is expected and have multi-speaker rules, set up Speaker Fadeout to above 3 seconds. At a minimum, we recommend setting it to above 1 second to avoid double switching/reframing on the same speaker.

Speaker Reactivity

Speaker Reactivity refers to the number of audio samples VisionSuite waits for before considering a speaker to be an active talker.

A lower reactivity will wait for longer to determine if a person is actually speaking. At the same time, since it waits longer, it gains higher confidence and accuracy on their coordinate positions. Nevertheless, a low reactivity will take longer to determine if someone is speaking, therefore leading to slightly slower switching speeds.

A high reactivity, in contrast, will take fewer audio samples of a speaker to determine their location and whether they’re speaking, triggering the downstream actions faster, but compromising with more inaccuracies in the confidence level and a talker’s location.

A speaker reactivity of 0.8 is recommended. If the reactivity is set to higher, the system will react before it has enough data to get a good shot. If the reactivity too low, it will reduce the switching speed too much. If that’s a compromise you’re willing to make to get significantly better shots, it is worth trying it.

Bottom line: Higher reactivity → faster switching (but could be more inaccurate)

VAD Sensitivity

Voice Activity Detection helps to mitigate false camera switches by differentiating ambient noise from speech, eliminating unnecessary distractions.

VAD operates as a speech-activated gate globally, preventing camera switching from noises only during periods of silence. Once speech is detected and the gate opens, it cannot prevent camera switching from ambient noise that occurs simultaneously while a person is speaking.

A high VAD sensitivity will be more prone to consider some forms of speech as noise, whereas a low VAD sensitivity may be more prone to consider some types of noise as speech.

You can set the VAD sensitivity value to 0 to disable VAD.

If using Shure MXA920 microphones, we recommend setting the VAD value to 0, and using Shure’s onboard VAD instead. A VAD sensitivity of 0.6 is recommended when using Sennheiser ceiling microphones. 

Far-End Peak Threshold

This parameter ensures that only audio signals higher than the set dB threshold trigger the signal of a speaker on the far-end. For example, if the far-end audio is lower than 20dB, the far-end rule would not be triggered to switch to an overview shot.

A Far-End Peak Threshold of -20dB is recommended.

Matching Sensitivity

Matching Sensitivity refers to the process of ‘fusing’ nearby detections in VisionSuite Designer.

If a microphone gets multiple detections from a single speaker, a high matching sensitivity will fuse them into a single detection (and therefore a single coordinate) to mitigate uncertainty.

However, if the sensitivity is too high, two adjacent speakers that are speaking right next to each other may be fused into a single detection and not trigger a camera to react to the new speaker.

Matching Sensitivity is therefore mostly important when using multiple ceiling microphones.

Matching Sensitivity is also applied to vision detections. If a vision camera sees a person in one location, and the audio data comes from the vicinity of that vision detection, both the visual detection and the audio detection will be merged to determine who in the camera’s view is talking.

A Matching Sensitivity of 0.4 is recommended. Above 0.9 will not be so useful, as it will most likely fuse different people into the same detection. If you see a lot of double detections, set Matching Sensitivity to 0.6. 

If using Shure’s ‘Optimize Tracking’ feature with reporter and follower microphone groups, VisionSuite’s Matching Sensitivity will be applied on top of Shure’s own clustering. Therefore, if setting low values between 0-0.4, you won't see a difference.

Reflective Acoustics

This parameter is useful if you have a room with a lot of hard surfaces and if you notice that framing often changes a lot depending on where people face when speaking. In rooms with a lot of relfections, turn the Reflective Acoustics toggle ON.

• For Shure microphones, this optimizes reflection and height-correction handling to improve localization behavior in reflective environments
• For Sennheiser microphones, this modifies VisionSuite’s internal modeling of detections uncertainty

High Background Noise

In situations where you have constant high ambient noise in the room, turn this toggle ON. It should not be needed in most rooms, especially if they follow our acoustic recommendations outlined in the Designing for VisionSuite guide.

• For Shure microphones, this optimizes VAD sensitivity and localization sensitivity to improve performance in noisy environments.
• For Sennheiser microphones, this optimizes the microphone sensitivity threshold to reduce false or unreliable detections caused by background noise.

Room Zone

The room zone defines the overall area in which the system will process detections. It should encompass all areas where you plan to create Speaker or Presenter Zones, with a small buffer around the edges to allow for movement and detection variance.

• Typically, the room zone can match the floor outline to include the entire space.
• Areas where you do not want automation—such as sources of noise or irrelevant regions—can be excluded from the room zone to prevent unnecessary detections.

This ensures the system only focuses on the areas that matter for camera automation.

Room Zone Height Limits

You can define minimum and maximum heights for the room zone to constrain which audio detections the system considers. Any detections below the minimum or above the maximum are ignored.

Example: Setting the minimum height to the table level prevents detections from below the table, reducing false triggers.

If performance of the system does not seem optimal, you can take these steps to validate the calibration. Make sure to turn on “raw mic data” in the settings and “persons data” in the camera streams. Make sure you are confident that you calibrated the system as instructed and do not change any settings, if not instructed to do so.

When both modes are active, the rules engine determines which camera goes live. Rules are prioritized by type (see below)

Rule types in order of priority from highest to lowest:

1. Far End — remote participant active
2. Multiple Zones Active — multiple zones triggered
3. Multiple People Talking — multiple speakers active
4. Single Person Talking — single speaker active
5. Multiple People Enters — multiple people entered in a zone
6. Single Person Enters — single person entered in a zone
7. Single Person Leaves — person left a zone
8. VIP is Lost — tracked VIP lost
9. No Zones Active / All Zones Silent — no zones active

In practice, this means Speaker Logic outranks Presenter Logic. If a speaker starts talking while the presenter is being tracked, the system will switch the live output to the speaker-spotlight camera.

Both containers continue to run on their respective cameras, regardless of which is live — the tracking camera keeps following the presenter even when it is not on air, so the switch back is seamless.

To enable camera automation, create a Trigger Zone by clicking the + icon next to Presenter zones in the left pane. Trigger Zones can trigger rules in Presenter Logic when activity is detected within the zone. Under Type, select Trigger. Then, select which camera the Trigger Zone should be assigned to from the drop-down menu. If required, click the toggle button to set the state to Enabled, this activates the Trigger Zone.

Use the camera video preview window to position the Trigger Zone over the area that you want to monitor for activity to start Presenter Tracking (for example, when a presenter enters). Adjust the Trigger Zone by dragging its corners.

Avoid making Trigger Zones too large, as this may cause tracking to activate when people simply pass by.

Avoid placing Trigger Zones over displays or in areas such as windows or corridors, where false detections may trigger tracking. In many cases, it may not be possible to avoid placing Trigger Zones over displays. In these situations, use Exclusion Zones (see below) to prevent false triggers caused by people appearing on the displays.

Once you’ve created your Trigger Zone, it is time to configure the rules that drive the presenter automation logic. In your config, head to the Presenter Logic drop-down menu and create a new presenter rule by clicking +.

All triggers are based on Enter, Leave, or VIP Lost events.

• Events are only generated from the portion of the Trigger Zone that is visible in the camera’s view.
• The Trigger Zone is used to take actions such as starting to track. However, leaving a Trigger Zone does not automatically stop tracking. To stop tracking, you need configure a One person leves rule or use a Tracking Zone with the VIP is lost rule. The latter is preferred, as the VIP is lost rule should always be configured to handle unexpected loss of the tracked person.

One Person Enters

The One person enters event is triggered when a presenter enters a zone and no other person is being tracked in that zone by any camera. A person is considered to have entered when a substantial portion of their head is fully within the Trigger Zone. For example, an arm or leg inside a Trigger Zone will not trigger an Enter event. For the rule to trigger, the person must remain within the zone for the duration of the hold time.

You also need to set the tracking camera and the container that is called to start tracking with the desired shot, and tick Switch Camera to ensure the camera is switched live once tracking has started.

Don’t forget to enable your rule - it won’t work otherwise. To enable it, use the toggle button next to the rule name.

Example: To start tracking, a person must enter a Trigger Zone and remain there for the duration of the hold time. Once this is met, the container (Section 1.3) associated with the Trigger Zone is activated. If the Switch Camera option is enabled, the camera feed will switch.

One Person Leaves

The One person leaves event works in a similar way and, when a camera is tracking, is only triggered when the tracked person leaves. When a person leaves a Trigger Zone, another action can be triggered, such as changing the shot size or stopping tracking. In most cases, this event is not required; instead, use the the VIP is lost event.

VIP is Lost

The VIP is lost event is not tied to a specific Trigger Zone. It is used to recall a fallback container when the presenter leaves the camera’s view - for any reason - or exits the Tracking Zone. In this case, the event is triggered when the entire body of the VIP (i.e., the tracked person) is fully outside the Tracking Zone. When this occurs, you will probably want to trigger a fallback home position container.

Multiple People are Inside

The Multiple people are inside event is triggered when the number of people visible in the Trigger zone (heads are what matters) becomes two or more. Once the number of goes back to one, the rule becomes inactive again.

A Tracking Zone helps to set the boundaries of your presentation area. It serves two functions: 1) when a presenter leaves a tracking zone a VIP is lost event is triggered that can be used to recall a fallback home position, and 2) it helps to exclude vision detections that are outside the camera's area of interest.

To create a Tracking Zone, select Tracking in the zone type drop-down menu, and in the camera feed preview, drag the corners of the Tracking Zone to delineate the area where you’ll want your presenter to be tracked. Anything beyond the Tracking Zone will be considered ‘out of bounds’.

Use the Tracking Zone to also exclude any seated audience that you don’t want to interfere with the tracking behavior.

Exclusion Zones allow you to define areas where detections are intentionally ignored by the visual logic. They are useful for eliminating unwanted detections, such as people shown on screens, and help prevent undesired camera triggers or logic events.

Exclusion Zones ignore a detection when at least 95% of the detection’s bounding box is covered by the zone. This means a tracked presenter should not be fully within an Exclusion Zone. Ensure the shot is zoomed out enough so that part of the presenter’s bounding box (for example, their legs) extends beyond the boundaries of the Exclusion Zone.

To create a Exclusion Zone, select Exclusion in the zone type drop-down menu, and in the camera feed preview, drag the corners of the Exclusion Zone to delineate the area where you’ll want your detections to be ignored.

Finally, it’s time to validate that your Presenter Logic works as expected.

Try whether your Trigger Zones are triggered within the defined hold time, and ensure that the Trigger, Tracking, and Exclusion Zone positions and shapes serve their functions and stay in their intended places.

We recommend running a couple of trial runs/rehearsals during actual presentations to identify any edge cases and adjust the logic afterwards to mitigate unintended behaviours.

On top of that, fine-tune your tracking shot containers, adjusting the deadband width, tracking smoothness, framing, relative size, etc to achieve your desired shots and tracking experience.

To interact with the room, users will likely want to have some control over how the system operates.

In the room’s touchpanel, the following functionality toggles will most likely be needed:

1. Switch between Room Configs (e.g. different room layouts)
2. Bypass VisionSuite

Controlling Room with VisionSuite

Any element of a Q-SYS system can be driven by control pins. You may wish to control room lighting, audio, or any other aspect of the room, and have this automated by VisionSuite.

This can be accomplished by using the LED output Control Pins from the VisionSuite component, which are available for each room, and connecting them to other Q-SYS components, including plugins for 3rd-party devices.

In VisionSuite Designer, each LED can be programmed to become true for any event in the Config.

Automation Ideas

1. An LED that becomes true while a Presenter Tracking rule is executing. This can be used to automatically fade out BGM and change the lighting when the presenter starts to be tracked. A second LED can be programmed to become true when the VIP is lost, which fades the BGM back in and changes the lighting again.
2. An LED that is true every time the audience asks a question, to bring up lighting on the audience

Example

1. In the properties of the VisionSuite component, ensure there are enough LEDs for the automation you want to perform.
2. Create the rules in the usual way. Here there is a rule for a presenter entering the Trigger Zone, and a rule for the Presenter leaving the Tracking Zone (VIP Lost).

3. Press the “Control Pins Configuration” button in the top bar of VisionSuite Designer.

4. Here you will see a row for each LED.
   1. Select Rules from the Config, and a Rule Status for each LED
   2. When the status of the Rule matches the Status you specify, the LED will become true, otherwise it will be false.

Rule Status Definitions

While you can select any status to set an LED, for most practical applications, it’s common to use Executing for a momentary pulse while the rule is getting from the Idle to the Live state, or Live if you want the LED to be true when the rule has completely finished.

 

 

When onboarding room users, make sure to explain that for the best performance, they should speak towards the direction of the microphone. Participants speaking more than 90 degrees off-axis away from the microphone will see less accurate framing. Also, verify that the switching speed and pacing of the silence rules are triggered to their liking and if not, adjust as needed.

Make sure to also explain the placement of trigger zones that are used to activate the tracking. Make them aware that moving key furniture (e.g. a lectern or whiteboard) will not move the Trigger Zone associated with that reference point. Users should also be aware of when they can expect issues (e.g. if hiding from the camera during tracking or crossing with multiple people while being tracked).